The mismatch between the actual and displayed keybinds is obviously bad, so unhardcoding these is wonderful!

However, I'm not sure displaying all the keybinding on this screen is the correct approach in the face of translations.
We already have the keybinds listed in the [?] keybinds menu, we kinda don't want to create new translation strings when we have already translated them in the [?] menu (for translators workload sake), and as you note yourself the new layout is a bit tight and will be even tighter in other languages (for example german already has to abbreviate the hell out of them)

Even in English I suspect you can get out of bounds when you bind all those things to Insert/Home/PageUp/PageDn/Backspace.

I think it's better to remove all of them (except maybe the [s]witch one) and replace with a [?] Keybindings. (It's a much smaller and less impressive PR, granted, but is still an improvement over the current master IMO)

If you think that displaying all of them here (at the cost of extra translation work) is still better (which is valid!), then at the least we need to size the vertical space dynamically and not hardcode it to 3 lines (but that might be a bigger overhaul)

I think it's better to remove all of them (except maybe the [s]witch one) and replace with a [?] Keybindings. (It's a much smaller and less impressive PR, granted, but is still an improvement over the current master IMO)

If you think that displaying all of them here (at the cost of extra translation work) is still better (which is valid!), then at the least we need to size the vertical space dynamically and not hardcode it to 3 lines (but that might be a bigger overhaul)

Personally, I have no problems at all with just removing all the help text and leaving a [?] Keybindings. I've done it in the past, too #40236. I like clean UIs, no clutter lol.
I feel like, as you imply, anyone can simply open the keybinding screen if they need help.

There are three other similar "manager" windows (auto notes, safe mode, color), and it'd make things a lot simpler for everyone involved if we do it this way.

How does this look 🤔

Using the longest key I can think of for the command here

How does this look

Not very good if I'm being honest.
True [BACKSPACE] Switch is hard to parse, and is somehow losing its context now that it's a bit visually further away from "Autopickup enabled"

Looking at this slimmer version, I feel that we don't need to display the switch keybind anymore (as in: the menu is not getting any less navigable if the keybind mention is gone).
If i hackishly remove it in paint, it looks okay to me:

Also I think if you can manage to put the [?] at the bottom of the screen, it would be better, but I don't feel too strongly about this one.
(And also, that time is probably better spent migrating the whole menu to ImGui 🙃 )

Not a problem, I can remove the unneeded text.

(And also, that time is probably better spent migrating the whole menu to ImGui 🙃 )

Unfortunately I don't have the skill level to migrate windows to ImGui... These minor changes are already tough enough for me.
I don't know when anyone will get around to the ImGui conversions, and I'd really like for these texts to not be hardcoded in the mean time. I want to contribute to ImGui conversions, but each time looking over related code I just don't understand it yet...